App Deployments
Last Updated: May 2025
Implementation Effort: Medium – Deploying apps to macOS devices in Intune requires planning, packaging (e.g., .pkg format), testing, and configuring deployment assignments and dependencies.
User Impact: Medium – Users may need to restart devices, accept prompts, or adjust settings depending on the app type and deployment method.
Introduction
Application deployment is a critical part of managing macOS devices in Intune. It ensures users have access to the tools they need while maintaining control over what software is installed and how it’s updated. Intune supports multiple app types for macOS, including Microsoft 365 apps, PKG installers, line-of-business (LOB) apps, and web links. From a Zero Trust perspective, app deployment is about ensuring only trusted, approved software is delivered to compliant devices—and that software inventory is visible and manageable.
This section helps macOS administrators evaluate their app deployment strategy and align it with Zero Trust principles—particularly around software integrity, access control, and user productivity.
Why This Matters
- Ensures only approved apps are installed on managed devices.
- Reduces attack surface by limiting exposure to unmanaged or unvetted software.
- Supports Zero Trust by enforcing app-level access control and visibility.
- Improves user experience by automating app delivery and updates.
- Enables auditability of app inventory and deployment status.
Key Considerations
Microsoft 365 Apps for macOS
- Intune provides a built-in option to deploy Microsoft 365 apps (Word, Excel, Outlook, etc.) as a suite.
- You can configure which apps to include and whether to auto-update.
From a Zero Trust perspective: Ensures that productivity tools are deployed from a trusted source, with centralized update control and license compliance.
PKG Apps
- PKG files are the standard macOS installer format and are fully supported by Intune.
- Most vendor-provided PKGs (e.g., Chrome, Edge) are already code-signed with a trusted Apple Developer ID.
From a Zero Trust perspective: Always verify the source of the PKG and ensure it is obtained directly from the vendor or a trusted internal source to maintain software integrity.